📝 Description

The changes simplify the handler logic by removing redundant path handling and ensuring that path additions are only applied when explicitly provided via headers.

🛠️ Changes Made

• Replaced getPathAndResourceNames in favor of a simplified getResourceNames.
• Updated handleRequest to extract pathAddition only from the pre-configured handler's targetPathHeader.
• Adjusted cache lookup functions to return only resourceNames instead of (path, resourceNames).

✅ Checklist

• I have tested the changes in this PR

🧪 Testing

• Dev QA
  • Created a function that prints the event.path
  • Triggered the function with this command:
    curl print-path.default-tenant.app.vmdev5.lab.iguazeng.com/a/b
  • Before changes:
    "name":"processor.http.w0.python.logger.connection-manager.event","message":"Request path","more":{"path":"/a/b/a/b"}}
  • After changes:
    "name":"processor.http.w0.python.logger.connection-manager.event","message":"Request path","more":{"path":"/a/b"}}
• Updated UTs and added more cases coverage

🔗 References

• Ticket link: https://iguazio.atlassian.net/browse/NUC-602
• Design docs links:
• External links: The second path append happens here

🚨 Breaking Changes?

• Yes (explain below)
• No

🔍️ Additional Notes

• Need to discuss weather we still want to support targetPathHeader [link]